home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Almathera Ten Pack 1: Comms & Networking
/
Almathera Ten on Ten - Disc 1: Comms & Networking.iso
/
jackingin
/
dnet2_10_13
/
amiga
/
readme
< prev
next >
Wrap
Text File
|
1995-04-30
|
6KB
|
150 lines
DNET V2.10
27 November 1989
NEW THIS RELEASE: 7 bit support.
DNET (c)Copyright 1987-1989 Matthew Dillon, All Rights Reserved
Matthew Dillon
891 Regal Rd
Berkeley, Ca. 94708
USA
...!ihnp4!ucbvax!dillon USENET
dillon@ucbvax.Berkeley.edu ARPANET
ucbvax.berkeley.edu pub/amiga ARPANET-FTP
WHAT IS DNET
DNet is a link protocol and should properly be called DLink, but
the name DNet stuck and so it will stay. DNet allows one to connect two
amigas together and run multiple connections between them. For example,
you can open a talk window or two or three and be doing an upload and be
doing a download all at the same time.
Currently, DNet can be used to connect two Amiga's together or
an Amiga to a 4.2BSD/4.3BSD compatible UNIX.
** AN 8 BIT PATH IS NO LONGER REQUIRED. DNET WILL NOW RUN OVER
7 BIT PATHS. (TAB,FF,CR,LF, 0x20-0x7F).
INSTALLING DNET ON YOUR AMIGA
(1) ## REMOVED, was copy dres.library to libs:. no longer required.
(2) copy the DNet binary and all client and server program to
somewhere accessable on your path.
(3) copy s/dnet.servers to s:
* modify s:dnet.servers so all server paths point to whereever
you stuck the servers
(4) copy s/dnet.config to s:
* you may have to modify s:dnet.config too ... look into the
DOC directory for more information.
CALL A FRIEND WHO HAS GOT DNET INSTALLED
1> RUN DNET -X -8 -b1200
NOTE: -h0 option in previous versions is now the default. Use -h1
to *enable* carrier detect checking.
7 bit mode is now the default. Use -m0 if you have an 8 bit
connection and want to take advantage of it.
PARITY NOTE: If your system forces parity you specify the
appropriate parity option with the -Z switch,
refer to dnet.doc
warning: The defaults for -X (manual mode) in S:DNET.CONFIG
turn off security. Please read documentation in the doc directory
for more information. This README file is only intended to get
you up and running. The above line also sets the baud to 1200...
the idea is you set it to what is proper for your modem. Again,
read DOC/DNET.DOC for more options and information.
A small DNET window should appear from which you can dialup your
friend's amiga. On CONNECT, DNET should automatically adjust the
baud rate. It may be necessary to modify S:DNET.CONFIG in this
regard (read the docs!)
After connecting, executing the START DNET menu option from either
end will start the protocol. The small dnet window should go away
and DNET should attempt to run the FTERM client program, which
connects to an STERM server program on the other end. Your friend's
amiga will do the same.
If all goes ok, it should flash the window size in the title bar
and you can type. If not, the window will go away and an error
message will be printed out in your CLI: "unable to connect".
WARNING: Even if there are no windows open (no clients active),
DNet is still running!!!! us the CLI BREAK command to kill DNet
and give you back the initial DNet window, from which you can
hit the close-window gadget.
breaking the DNet protocol will kill any active clients.
SERVERS AND CLIENTS
DNet has a notion of servers and clients. That is, you run the
protocol as described above, then run other external programs that talk
to the core program "DNet". These other external programs "FTerm",
"GetFiles", "PutFiles", etc... obtain virtual connections to special
server programs on the remote machine.
Thus, when you started the protocol above DNet automatically
ran the FTERM client... you can run as many FTERMs as you have memory
for (well, actually, DNet is limited to 64 simultanious channels). When
a client program such as FTERM is run on computer A, it causes the
appropriate server program (STERM in this case) to automatically be run
on computer B. The client and server need some way to rendezvous, and they
do this by giving the same PORT NUMBER to the protocol driver.
This is what the S:DNET.SERVERS file is ... when you run a client
on computer A it asks for server #<blah> (e.g. 8195 for an FTERM) on the
remote machine. computer B (the remote machine) looks up 8195 in the
S:DNET.SERVERS file, finds the path to the server in question, and runs it
automatically.
PORT CLIENT SERVER PURPOSE
8192 PutFiles SCopy send files to remote computer
8195 FTerm STerm open a talk window on both computers
8196 CLITerm SCli remote-CLI (actually newshell)
8197 LoadAv ------ Load-Average window (when running DNet
to a UNIX machine)
8198 ------ SPrint printer server
8199 ------ SPasswd password server. Used to gain security
access for auto-answer callups
8201 GetFiles SGCopy download files from remote computer
NOTE: FTERM may be used to connect to arbitrary ports that otherwise have
no associated client. see the docs for FTERM.
READ THE DOCS FOR EACH OF THESE CLIENTS
SECURITY
Read DOC/DNET.DOC and documentation for each client/server. DNet
implements various levels of security. This is intended for BBS
support but I have not finished my DNet-BBS program yet. The security
is still there, however.
One example: If the DNET_READ security option (env: var is set
automatically from S:DNET.CONFIG depending on the option you give
DNET when you first run it) is anything less than 9, the SGCopy
server for GetFiles will only allow uploading from directories with
their comment field set a certain way. That is, you can control
exactly what you allow other people to download.